**********************************************************************

                     Array1000SA Family v3.30.08

                                and

            Adaptec CI/O Management Software v3.30

                            Readme File
                         
                           July 08, 1998

**********************************************************************

This file contains the following:

  - WHAT IS IN Array1000SA FAMILY V3.3

  - NOTES ON ADAPTEC CI/O MANAGEMENT SOFTWARE V3.3

  - COMPATIBILITY NOTES FOR ADAPTEC Array1000SA FAMILY PRODUCTS

  - HARDWARE INSTALLATION NOTES 

  - Array1000SA TEST NOTE

  - GENERIC ARRAY CONFIGURATION NOTES

  - KNOWN PROBLEMS

**********************************************************************


WHAT IS IN Array1000SA FAMILY V3.3
==================================

Array1000SA is a server release of Adaptec's RAID product family.
The current product supports systems running Windows NT 4.0, 3.51 and 
NetWare 4.11, 3.12. 

The following features are included:
 RAID levels 0, 1, 5 and 0/1
 AAA-130SA series array adapters 
 ARO-1130SA RAID Option Card supporting:
  Selection Utility for automatic flashing of proper BIOS
   and selection of proper driver disk (A or B) supporting
   AIC-7895B2, AIC-7895C or AIC-7880B motherboard SCSI
 S.M.A.R.T. disk drive predictive failure notification 
 CI/O Management Software V3.3 supporting:
  Adaptec SCSI host adapters, such as the AHA-2940UW
  Adaptec External Bridge Array controllers
  SNMP 
  DMI Version 2 
  SAF-TE enclosure management support
 INT13 Extensions and VDS
 BIOS Boot Specification support

**********************************************************************


NOTES ON ADAPTEC CI/O MANAGEMENT SOFTWARE V3.3
==============================================

READING README.TXT DURING CI/O SETUP
------------------------------------
Attempting to read this readme.txt file during CI/O setup may 
result in a delay of up to 3 minutes when exiting the notepad 
utility.  The setup utility will then continue with the setup 
process.  

USE OF LARGE FONTS
------------------
The use of large fonts is not supported.

USE OF TAB AND ARROW KEYS
-------------------------
The use of Tab and arrow keys to navigate the Configuration window 
is not supported.

TRUNCATED STRINGS
-----------------
CI/O truncates words that are too long to display in the space 
available. A tilde "~" symbol is inserted in the next-to-last 
available character space, and the last character of the string 
fills the last available character space.  For example, in a 12 
character field, the string "Finance Array #3" becomes "Finance 
Ar~3".  The full text can be read by double clicking on the object 
to display the Detailed Information dialog box.

CONFIGS.DAT
-----------
CI/O Management Software automatically creates the configuration 
file CONFIGS.DAT in the client directory. The file is used by 
networked clients to store a list of servers to which the client 
is connected.  If the CI/O software is uninstalled, this file must 
be manually deleted.

LOG SEVERITY ICON COLORS
------------------------
Highlighting the small severity icons at the beginning of each server 
log entry changes the color of the highlighted icon without changing
the severity level.

HOURGLASS ON TASK COMPLETION
----------------------------
When issuing certain commands, the cursor may still remain as an 
hourglass when the task has completed. To correct this, move the 
mouse.

DISPLAY OF SCSI SCANNER DEVICES
-------------------------------
Some scanner models report to the SCSI host adapter as a generic 
SCSI device, rather than as a scanner.  They may not be displayed 
on the CI/O physical resources map.

CI/O VERSION DEPENDENCIES IN CONNECTING CLIENTS TO SERVERS
----------------------------------------------------------
CI/O v1.0 and v2.x are incompatible with the CI/O v3.x release. In 
order to use CI/O, upgrade the client to CI/O Management Software 
v3.3.  Thereafter, the following rules apply:

1. At a given server or client all the CI/O sub-components must be 
   at the same version level.
2. The CI/O client application will be capable of interacting with 
   the CI/O server application, if the client major version number 
   is    the same as the server, and if the minor version number 
   (tenths' digit) is equal or greater than that of the server.

Examples:
a. A client v2.00 will work with a server v2.00, because they have 
   the same major number.
b. A client v2.50 will work with a server v2.40, because the client 
   minor version number(.50) is greater than the server minor version 
   number (.40).
c. A client v3.00 will not work with a server v2.60, because they 
   have different major numbers.  The client has a major version 
   number of 3 and the server has a major version number of 2.
d. A client v2.14 will work with a server v2.19, because the client 
   minor version number is less than the server version number but 
   within the tenths' digit.

RE-CONNECTING FROM A CLIENT AFTER LOSING CONNECTION TO A SERVER
---------------------------------------------------------------
For certain operations, the networked client will establish an open
connection with the server, and will maintain the connection until 
the operation is finished.  The specific cases where this occurs are 
when the following two conditions are met:

1) A Reconstruct, Verify, Initialize, or Test All Spares activity is 
   running on the server, and

2) The user opens the Activity View or a Watch Box to view the 
   progress of the activity.

These activities may take considerable time to complete, and on a 
busy network a connection may be lost.  It should be possible to 
determine whether this situation has occurred by viewing the contents
of the Current Event Log.

If the above mentioned operations stop, make sure that there exists a
good network connection to the server by double clicking on the 
server icon. After reopening the activity window, the progress bar 
should display the current status of the operation.

ACTIVITIES SCHEDULED MULTIPLE TIMES
-----------------------------------
A given CI/O activity should not be scheduled more than once to run 
at a specific time.  Multiple events may otherwise be generated.

PROBLEMS ACCESSING THE SERVER LOG FILE IOMGR.LOG
------------------------------------------------
In extremely rare circumstances, entries in the Server Log file 
"iomgr.log" may become unreadable. This occurs when the file format 
is no longer as expected, perhaps due to client and server software 
revisions being out of sync. Should this happen, the situation will 
be automatically detected and the existing file will be renamed to 
"iomgrlog.old".  Then, a new log file "iomgr.log" will be created 
and subsequent events entered to that new file. Furthermore, an 
event will be posted in the new log, stating "Server Log database 
cannot be read. Database Reinitialized." 

If only a specific record in the log is found to be in error, the 
log will continue to report all valid records.  The entry for that 
specific log event, however, will say "No data available for this 
entry."

USE OF CI/O WITH NETWARE SERVERS
--------------------------------
If using an Ultra-2 SCSI host adapter with the FMS v3.01 (or later) 
drivers for NetWare, be sure to also load the NWASPI.CDM driver.  
Otherwise, CI/O cannot manage the adapter and connected devices.

The CI/O v3.30 release cannot be installed along with the Small 
Business application suite for NetWare v4.11.  At the time of 
release, a workaround to the conflicting NLM modules is being sought 
by Adaptec and Novell.

Installing the Novell NetWare components of CI/O to a server with a 
very large SYS volume (>2 GBytes) may result in a low disk space 
error message.  This can be ignored.

If the remote client tends to disconnect from a NetWare 3.x or 4.x 
server, the TIRPC components installed by CI/O on the server may have 
been overwritten by an older version.  This can occur when various 
other applications are installed on the server.

USE OF CI/O WITH ARRAY1000SA CONTROLLERS
----------------------------------------
If all disk drives connected to the Array1000SA controller's channels 
are members of a single array, and that array goes off-line, then the 
CI/O display will change. This occurs because the array driver unloads 
from the system.  The CI/O Management Software will no longer display 
any array controller, channels, or array drives.  If all members of an 
array are missing, the array and its members are not displayed after a 
reboot or Rescan operation.

In the rare circumstance that an array created on an Array1000SA 
controller has multiple device failures and goes off-line, a critical 
event will be posted to notify the user.  In certain situations, a 
second event may also be received, stating that the array is critical.  
The second event should be ignored.

Upon Reconstruct of a critical RAID 0/1 array using a Pool Spare, the 
new member may be marked as "down" (red arrow through the icon) until 
reconstruction completes.

USE OF CI/O WITH EXTERNAL ARRAY CONTROLLERS
-------------------------------------------
For best operation of CI/O with external array controllers, the user
should turn ON the Temperature option in the controller.  This is
accessed from the SEP Config menu.

Event Log notifications may be confusing when deleting arrays on an 
external controller.  To avoid this situation, turn OFF the SAF-TE 
Drive Slot support on the external controller.  This is accessed 
from the SEP Config menu.

CI/O maintains a separate server event log, and does not directly 
access the log maintained by the external array controller.

Support of Novell NetWare with Adaptec external array controllers 
requires certain configuration adjustments.  The array controller 
must be configured to be at LUN-0, and SAF-TE support on the array 
controller must be disabled.  Refer to documentation supplied with 
your controller.

CI/O does not support certain features of the external array 
controller:
- change the date and time of the bridge
- change the bridge target ID
- set LUN numbers when you create an array
- set parameters such as backoff % and initiator ID
- low-level Format of arrays and singles

The external array controller does not support certain features 
of CI/O:
- creation of pool spares
- creation of single-drive RAID-0 arrays
- Down a Drive operation

Adaptec external array controllers automatically initialize new arrays 
upon creation.  This operation cannot be deferred to a later time.

USE OF CI/O WITH DMI AND SNMP
-----------------------------
If attempts are unsuccessful to make the ciodmi service start 
automatically, review the syntax of the "Depends On" entries in the 
Windows NT Registry.  Enter a carriage return after each dependent 
entry.

When upgrading CI/O to a newer version, make sure to update the 
corresponding DMI MIF or SNMP MIB to the same level.  Otherwise, 
displayed values may be incorrect.  To update the MIF on Windows NT, 
stop the CIODMI service, open a console window, change to the CI/O 
installation directory (where CIODMI.EXE and CIO.MIF should be 
located) and type:
    ciodmi r
After the MIF is reloaded, type control-C to exit, and restart the 
CIODMI service.  To update the MIF on NetWare, instead of "load 
ciodmi" type "load ciodmi r".

With early versions of DMI Service Layers and browsers used with 
Novell NetWare, intermittent loss of event notification has been 
observed when using the SPX/IPX protocol.  The TCP/IP protocol has 
not exhibited this behavior.

After unloading ciodmi for NetWare, a message may be observed 
indicating that not all resources were released.  This appears to

be a problem in the DMI Service Layer for Novell NetWare and is not 
related to CI/O.

The DMI 2.0 SDK for NetWare has been found to install an older version
of TIRPC, potentially overwriting the version installed by CI/O.  See
comments in section "USE OF CI/O WITH NETWARE SERVERS."

RESTORING COOPERATION BETWEEN CI/O AND INTEL LANDESK V2.5
---------------------------------------------------------
Customers using certain versions of Intel LANDesk as their work group 
management solution may experience problems when simultaneously using 
Adaptec CI/O Management Software.  The situation arises because some 
versions of Intel LANDesk include an older version of the CI/O 
software for use in monitoring SCSI adapters via the Desktop 
Management Interface (DMI.)  The LANDesk product loads the SCSI 
monitoring software by default.  CI/O Management Software, however, 
only allows a single copy of CI/O to run on the system at one time.

The work around consists of disabling either the SCSI monitoring 
software or the management software.  The user must decide, therefore, 
which capability is most important for their system configuration and 
use.  In general, if the system includes a disk array controller 
product from Adaptec, we advise that the SCSI monitoring functionality 
of LANDesk be disabled.

Software Installation Process:
1.  Install Windows NT and the updated Windows NT Server Pack, per 
    instructions for the Adaptec controller being used.  If Windows NT 
    is to be installed upon a "bootable" disk array, the user should 
    refer to instructions on the use of Adaptec ArrayConfig software.
2.  Install CI/O Management Software, per the Adaptec instructions.
3.  After rebooting the system, go to the Services dialog box within 
    the Windows NT Control Panel.   For each of the following, change 
    the entry from Automatic to Manual, and then stop each service:
        CIO Array Management Service
        CIOArrayManager RPC Command
        CIOArrayManager RPC Event
4.  Install Intel LANDesk, per the appropriate instructions, then 
    reboot the system.

To Use Adaptec CI/O Management Software:
1.  Go to the Services dialog box in the Windows NT Control Panel.
2.  Stop the CIORAIDManagement Service.
3.  For each of the following, start each service:
        CIO Array Management Service
        CIOArrayManager RPC Command
        CIOArrayManager RPC Event

To Use the Native SCSI Monitoring Feature within Intel LANDesk:
1.  Go to the Services dialog box in the Windows NT Control Panel.  
    For each of the following, change the entry from Automatic to 
    Manual, and then stop each service:
        CIO Array Management Service
        CIOArrayManager RPC Command
        CIOArrayManager RPC Event
2.  Start the SCSIDMI service and CIORAIDManagement Service. 

**********************************************************************


COMPATIBILITY NOTES FOR ADAPTEC Array1000SA FAMILY PRODUCTS
===========================================================

NETWORK CARD CONFIGURATIONS
---------------------------
Some uncommon network card configurations may cause the array 
configuration to hang. If the array configuration utility hangs, 
check for conflicts with the network card configuration.

AHA-2940
--------
Memory errors or other problems may be experienced if both AHA-2940 
and Array1000SA Family product coexist. To solve this problem, 
upgrade the AHA-2940 BIOS to the most recent version, v1.24 or later. 
If both ARO-1130SA and the AHA2940 are installed in the same system, 
one of the cards may not be visible by the operating system. This 
problem is caused by the system BIOS. Correct this problem by 
enabling the shadow RAM for all the address ranges in the system 
BIOS setup.

EZ-SCSI 4.0 & 5.0 SUPPORT
-------------------------
EZ-SCSI is not supported on Array1000SA products, however, 
ASPI8DOS.SYS is required for NetWare operations and is provided as 
part of this product. If ASPI8DOS.SYS is already installed, it 
should be upgraded to the version provided in the DOS directory of 
the Array1000SA FMS driver diskette.

ATI VIDEO CARDS
---------------
All ATI SVGA drivers may conflict with CDA1000 drivers under Windows 
NT. Use only standard VGA drivers with an ATI video adapter card 
under an NT environment.

SHARING PCI INTERRUPTS
----------------------
Do not configure the system to share interrupts between the 
Array1000SA Family product and any network interface cards (NICs)in 
the system. Refer to the system BIOS manual for information on how 
to configure PCI interrupts, or change the PCI slot in which the NIC 
is installed.

PROPER SCSI TERMINATION
-----------------------
It is important to properly terminate both ends of the SCSI bus for 
the ARO-1130SA card to function well. Improperly terminated SCSI 
busses can still operate under lightly loaded situations (only a 
couple of drives.)  SCSI bus scans will generally work, and find 
all devices even if termination is incorrect. Under heavy workloads, 
improper termination leads to SCSI bus errors and data corruption. 
Refer to motherboard/system documentation for termination 
instructions.

REMOVABLE DEVICES AS PART OF A RAID ARRAY
-----------------------------------------
Removable storage media devices cannot be part of a RAID array.

CD-ROM CHANGERS
---------------
CD-ROM changers are not supported under NetWare. 

HIGH PERFORMANCE CD-ROM DRIVES
------------------------------
Active termination may be required with CD-ROM Drives supporting the 
FAST SYNCHRONOUS (10MB/sec) negotiation or higher.  In general, 
failing to install proper termination or incorrectly setting 
negotiation speeds within SCSI Select may affect CD-ROM function-
ality, resulting in installation and CD-ROM access errors. Consult 
your CD-ROM drive vendor for proper termination information.

**********************************************************************


HARDWARE INSTALLATION NOTES
===========================

HARDWARE INSTALLATION - ARO-1130SA CARD CONFIGURATION INFORMATION
-----------------------------------------------------------------
When installing or re-installing the ARO-1130SA hardware into the 
system, SELECT OPTION "YES" for Reset System Configuration in the 
system BIOS setup. This ensures all configuration/resources are 
built properly for the current hardware in the system.

FLASHING: AAA-130SA SERIES
--------------------------
Specific system configurations fail to allow the AAA-130SA Series
BIOS to be flashed (with the Array10000 BIOS & Driver Selection 
Utility.) To remedy, follow the specified work around chart below. 

 SYSTEM                 WITH HARDWARE         SYMPTOM/
                                              WORK AROUND DESCRIPTION
 ------                 --------------------   ----------------------
 Dual Pentium II        ANA-6944 + AAA-13xSA  Remove ANA-6944 prior 
 IBM Netfinity 3500                           to running flash   
 IBM IntelliStation                           utility
 Intel DK440LX

BOOT FAILURE: (PCI CARD SLOT ORDER) AAA-130SA SERIES
----------------------------------------------------
Certain systems are sensitive to the order in which PCI cards are 
scanned by PCI Memory during boot up. If PCI cards are installed in
the wrong order, some systems may not see the AAA-130SA Series BIOS
and therefore fail to boot (hanging the system). To remedy, re-order
the PCI cards and re-boot.

**********************************************************************


Array1000SA TEST NOTE
=====================

The Array1000SA BIOS will not boot unless at least one device is 
attached to the Array1000SA family product. However, the product's 
BIOS will run its self-test diagnostic upon power-on. 

**********************************************************************


GENERIC ARRAY CONFIGURATION NOTES
=================================

INITIALIZING THE ARRAY
----------------------
If the user has created the array without initializing it, and reboots 
the system, the state of the array will be reported as:
        "New array needs init, needs system reboot"
A reboot at this point is not required.  One can initialize the array, 
and the array will become fault tolerant.

SUGGESTIONS ON DISK DRIVE WRITE CACHING
---------------------------------------
Most disk drives allow write caching, which greatly speeds up writes 
to disks. This feature enables an application program to continue 
executing once write data is successfully sent to a drive.  In very 
rare cases a deferred write error can occur (for example, because of 
a parity error within the drive cache memory.)  A deferred write 
error means data has been incorrectly written and is no longer 
available to the I/O system. The error is unrecoverable. If the 
consequences of this potential problem are unacceptable, the drives 
should be put in the "write cache disabled" mode.

HOT SWAPPING DEVICES ON ARRAY CONTROLLERS
-----------------------------------------
Hot swapping a device with another device of different type having 
the same SCSI IDs (replacing a CD-ROM with disk or vice versa) is 
not supported. 

REINSERTION OF DEDICATED SPARES
-------------------------------
If a dedicated spare is removed by mistake, upon reinsertion and bus 
rescan, it may become a single.  If this occurs, simply re-classify 
the single as a dedicated spare.

**********************************************************************

KNOWN PROBLEMS
==============


**********************************************************************

                                  END OF

                        Array1000SA Family v3.30.7

                                   and

               Adaptec CI/O Management Software v3.30
          
                                Readme File
                         
**********************************************************************

